Generic editor for databases

ABSTRACT

Facilitating generic database editing to allow for data to be received from a user for entry into a database without requiring the data to conform to schema constraints for the database. A method includes examining a first schema for a first database. The first schema including a first set of constraints specified in the first schema on data to be entered into the first database. The method further includes, based on the examination, constructing a second database corresponding to the first database. The second database is associated with a second schema with a second set of constraints. The second set of constraints is a relaxed version of the first set of constraints specified in the first schema.

BACKGROUND Background and Relevant Art

Computers and computing systems have affected nearly every aspect ofmodern living. Computers are generally involved in work, recreation,healthcare, transportation, entertainment, household management, etc.

Computing systems can include databases for storing, organizing andlinking data. Data is often stored in database according to a tightlycontrolled schema which includes constraints on how data is to beorganized in the database. Data can be edited in the database or enteredinto the database if the constraints are strictly followed. However, ifthe constraints are not followed, the database will typically not allowthe data to be entered. For example, a schema may specify that entriesinto a particular column or field be of a certain type, say for example,an integer type. If a user attempts to input an entry that is not of theinteger type into such a field, the database will reject the entry andnot allow the user to enter the data into the database.

Databases may have other constraints as well. For example, a databasemay have a schema with a constraint that indicates that if certainentries are made, other entries must be made as well for the certainentries to be committed to the database. For example, a database mayhave a constraint that indicates that if a name is entered into a namefield, corresponding address and telephone numbers must be entered aswell for the name to be committed (and finally entered into) thedatabase. If a user attempts to enter a name, or group of names, into adatabase but does not have immediate ready access to either the addressor telephone number, the name entries may be lost and need to bereentered once the user has access to the address and/or telephoneinformation.

Additionally, a user may be able to enter data directly into an editinginterface directly associated with the database, but may have difficultyusing generic data editors to enter data into a database. In particular,the generic editor may not be aware of schema constraints, and thuscannot direct a user to make appropriate entries. In particular, thegeneric editor may not be aware of triggers, stored procedures, checks,concurrency requirements, etc. or may not be able to provide sufficientcontext in that the generic editor does not have access to data forforeign key, unique key, and primary key information.

The subject matter claimed herein is not limited to embodiments thatsolve any disadvantages or that operate only in environments such asthose described above. Rather, this background is only provided toillustrate one exemplary technology area where some embodimentsdescribed herein may be practiced.

BRIEF SUMMARY

One embodiment described herein includes a method that may be practicedin a computing environment. The method includes acts for facilitatinggeneric database editing to allow for data to be received from a userfor entry into a database without requiring the data to conform toschema constraints for the database. The method includes examining afirst schema for a first database. The first schema including a firstset of constraints specified in the first schema on data to be enteredinto the first database. The method further includes, based on theexamination, constructing a second database corresponding to the firstdatabase. The second database is associated with a second schema with asecond set of constraints. The second set of constraints is a relaxedversion of the first set of constraints specified in the first schema.

Another embodiment includes a method that may be practiced in acomputing environment. The method includes acts for facilitating genericdatabase editing to allow for data to be received from a user for afirst database without requiring the data to conform to a first schemafor a first database. The first schema includes a first set ofconstraints on data to be entered into the first database. Method stepsmay be performed at a second database corresponding to the firstdatabase. The second database is associated with a second schema with asecond set of constraints. The second set of constraints are a relaxedversion of the first set of constraints specified in the first schema.The method includes receiving user input for the second database. Theuser input includes data complying with the second schema. The methodfurther include storing the user input in the second database separatefrom the first database.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Additional features and advantages will be set forth in the descriptionwhich follows, and in part will be obvious from the description, or maybe learned by the practice of the teachings herein. Features andadvantages of the invention may be realized and obtained by means of theinstruments and combinations particularly pointed out in the appendedclaims. Features of the present invention will become more fullyapparent from the following description and appended claims, or may belearned by the practice of the invention as set forth hereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and otheradvantages and features can be obtained, a more particular descriptionof the subject matter briefly described above will be rendered byreference to specific embodiments which are illustrated in the appendeddrawings. Understanding that these drawings depict only typicalembodiments and are not therefore to be considered to be limiting inscope, embodiments will be described and explained with additionalspecificity and detail through the use of the accompanying drawings inwhich:

FIG. 1 illustrates a computing environment including a first databaseand a parallel database to the first database;

FIG. 2 illustrates a method of facilitating generic database editing;and

FIG. 3 illustrates another method of generic database editing.

DETAILED DESCRIPTION

Some embodiments described herein are directed to storing databaseentries for a first database in a parallel database. The paralleldatabase is associated with a parallel schema with constraints that arenot as strict as constraints in a schema for the first database. Forexample, even though the first database has a row or field withconstraints in a schema that requires entries in that row or field to beof type integer, the second database may include a schema with no typeconstraints in a corresponding row or field. In some embodiments, thismay allow a user to edit data for entry into the first database withoutbeing constrained by the stricter requirements of the first database. Insome embodiments, this allows a user to enter what data they haveavailable and to persist such information until the information can bemade to comply with the stricter requirements of the first database. Inother embodiments, this allows for generic data editors to be used toenter information for the first database.

Embodiments may also be implemented which allow for a user to enter thedata for the first database into the parallel database withoutconforming strictly to constraints for the first database, but yet theembodiments provide warnings or messages to a user indicating that thedata does not comply with constraints for the first database. Thisallows a user to take corrective actions before trying to merge the datafrom the parallel database into the first database. Embodiments may beable to accomplish this functionality by examining the schema for thefirst database such that a system can determine if entries into theparallel database comply with constraints from a schema for the firstdatabase.

Additionally or alternatively, embodiments may include functionality forsurfacing warnings from the first database to a user. For example, if anattempt is made to merge data from the parallel database into the firstdatabase, and the merge is not able to be completed due to the firstdatabase throwing an exception, information about the exception can besurfaced to a user. Illustrating a number of specific examples, errorsmay be raised by the first database as a result of actuation oftriggers, a check, or a concurrency violation. Additionally oralternatively, when errors are raised, these may be logged to allow adeveloper to develop embodiments that can alert a user entering datainto the parallel database without needing to attempt to merge data fromthe parallel database into the first database. In particular, adeveloper may not be able to ascertain some database requirements simplyby examining constraints in the schema for the first database, as thoserequirements are only manifest as the result of a trigger in thedatabase being actuated, a check predicate not being satisfied, data notbeing able to be committed due to concurrency violations, etc.

Referring now to FIG. 1, an example embodiment is illustrated. FIG. 1illustrates a first database 102. The first database 102 includes a datatable 104. Associated with the data table 104 is a schema which includesa set of constraints 106. The constraints 106 specify restrictions ondata that can be entered into the data table 104 and the database 102.For example, the constraints may indicate that entries into a particularcolumn or field of the table 104 be of a certain type, say for example,an integer type. If a user attempts to input an entry that is not of theinteger type into such a field, the database will reject the entry andnot allow the user to enter the data into the database 102. In anotherexample, the database 102 may have a schema with a constraint thatindicates that if certain entries are made, other entries must be madeas well for the certain entries to be committed to the database 102. Forexample, a database may have a constraint that indicates that if a nameis entered into a name field, corresponding address and telephonenumbers must be entered as well for the name to be committed (andfinally entered into) the database.

FIG. 1 further illustrates a parallel database 108 which acts as a localrepository for data that can later be entered into the database 102. Theparallel database 108 includes a data table 110. The data table 110 hascolumns rows and/or fields that correspond to columns rows and/or fieldsin the data table 104. However, the data table 110 is associated with aschema with a set of constraints 112 that are not as restrictive as theset of constraints 106. Thus, data that may not normally be able to beentered into the data table 104 can be entered into the parallel datatable 110. Problems with the data in the data table 110 can later beresolved so that the data can then be entered into the data table 104.

FIG. 1 further illustrates a data editor application 114. The dataeditor application 114 may be, for example, a generic editor that doesnot necessarily understand constraints or other requirements for databeing entered into the database 102.

The following discussion now refers to a number of methods and methodacts that may be performed. It should be noted, that although the methodacts may be discussed in a certain order or illustrated in a flow chartas occurring in a particular order, no particular ordering isnecessarily required unless specifically stated, or required because anact is dependent on another act being completed prior to the act beingperformed.

Referring now to FIG. 2, a method 200 is illustrated. The method 200 maybe practiced in a computing environment. The method 200 includes actsfor facilitating generic database editing to allow for data to bereceived from a user for entry into a database without requiring thedata to conform to schema constraints for the database. The method 200includes examining a first schema for a first database (act 202). Thefirst schema may include a first set of constraints specified in thefirst schema on data to be entered into the first database. For example,FIG. 1 illustrates constraints 106 on data entered into the database102. By examining the schema that includes the constraints, a user candetermine constraints, or fields for a second database.

The method 200 further includes constructing a second databasecorresponding to the first database (act 204). The second database isassociated with a second schema with a second set of constraints. Thesecond set of constraints is a relaxed version of the first set ofconstraints specified in the first schema. Constructing a seconddatabase may include constructing the database in main memory and/or inone or more computer readable storage media of a computing system. Thecomputing system may include appropriate processing hardware forinteracting with the computer readable storage media. In one example,processing hardware may include functionality for reading from andwriting to the database. FIG. 1 illustrates an example of a paralleldatabase 108 which is one example of the second database. FIG. 1 furtherillustrates constraints 112 which may be part of a schema with relaxedconstraints. In particular, the constraints 112 may be relaxedconstraints for the second schema.

Illustratively, in one embodiment, the first set of constraints mayinclude a constraint that restricts field entries in a field in thefirst database to a limited set of one or more types. In contrast, thesecond set of constraints for the second database includes acorresponding constraint that allows corresponding field entries in acorresponding field in the second database to be of a type not includedin the limited set of one or more types. For example, constraints forthe first database may limit entries in fields to integer type objects.In contrast, constraints for corresponding fields in the second databasemy allow integers, floating points, strings, or other data types to beentered.

Illustrating another example, the first set of constraints may include aconstraint that restricts field entries in a field in the first databaseto be unique or primary keys. A unique key is a given entry in a columnin which no other entries in the column are identical to the givenentry. Similarly, a primary key is a given entry in a column in which noother entries in the column are identical to the given entry and whereno entries in the column can be null. Embodiments may be implementedwhere the second set of constraints includes a corresponding constraintthat allows corresponding field entries in a corresponding field (i.e.the corresponding field in the second database corresponds to a field inthe first database) in the second database to be entries that are notunique or valid primary keys.

In one embodiment, the first set of constraints may include a constraintthat restricts field entries in a field in the first database to alimited set of foreign keys. The second set of constraints includes acorresponding constraint that allows corresponding field entries in acorresponding field in the second database to not be limited to alimited set of foreign keys.

The second database may be associated with a set of one or more computerimplemented modules configured to receive data from a user, determinethat the data received from the user complies with the constraints inthe second schema, in response to determining that the data receivedfrom the user complies with the second set of constraints in the secondschema, store the data received from the user in the second database, inspite of the data received from the user being stored in the seconddatabase, determine that the data received from the user does not complywith the first set of constraints for the first schema for the firstdatabase; and in response to determining that the data received from theuser does not comply with the first set of constraints for the firstschema for the first database, surface to the user that the data doesnot comply with the first set of constraints for the first schema forthe first data base. For example in some embodiments, the seconddatabase may be associated with computer modules that are able todetermine that even though data may comply with the constraints for thesecond database, the data would not comply with constraints for thefirst database. Considering that the ultimate goal may be to enter datafrom the second database into the first database, it may be useful toassist a user in making data compliant with the constraints on data forthe first database. In one embodiment, when the second database isassociated with computer modules that can evaluate data to theconstraints for the first database, the computer modules may also send amessage to a user indicating that the data does not comply with theconstraints for the first database and/or that the information on whythe data does not comply with the constraints for the first database.

As noted, it may ultimately be an objective to merge the data in seconddatabase into the first database. Thus, in some embodiments, the seconddatabase may be associated with a set of one or more modules configuredto attempt to merge data from the second database into the firstdatabase. For example, these modules may be able to invoke databasecommands on the first database to move entries from the second databaseto the first database. However, in some situations, data may not be ableto be merged from the second database to the first database. Thus, insome embodiments, the second database is associated with computermodules configured to receive a notification from the first databasethat the data from the second database cannot be merged into the firstdatabase including information about why the data from the seconddatabase cannot be merged into the first database and surfaceinformation about why data from the second database cannot be mergedinto the first database. The second database may continue to store thedata in the second database in the second database to allow the user anopportunity to correct defects in the data in the second database thatprevent the data in the second database from being merged into the firstdatabase.

Data may not be able to be merged for any one of a number of differentreasons. For example, data from the second database may not be able tobe merged into the first database for at least one of data in the seconddatabase not complying with a predicate of a check for the firstdatabase, data being rejected as a result of a executing program scriptslike triggers in the first database based on data from the seconddatabase, or data being rejected as a result of a concurrency exceptionin the first database when an attempt is made to enter data from thesecond database into the first database.

Fields of a database may often be associated with one or more checks todetermine valid data that may be entered into the fields. These checksare not typically reflected in the constraints of the schema of thedatabase. Rather, the database includes programmatic modules configuredto evaluate one or more predicates of a check, and if the predicates aresatisfied when an attempt to enter data into the database is made, thenthe data can be entered. Otherwise, an error is raised and the data isnot allowed to be entered. Because often the predicates for the checkscannot be determined from the schema, in some embodiments, the seconddatabase and programmatic code associated with it may not be aware ofthese checks until an attempt to merge data from the second databaseinto the first database is made. Thus, embodiments may includefunctionality for surfacing errors and/or related messages due to notmeeting the requirements of a check predicate to a user of the seconddatabase so that the user can correct any problems with the data.

Similarly, databases may include programmatic code with triggerfunctionality. For example, data being entered into a database mytrigger actions by the database, which may invalidate other databaseentries or add additional requirements for certain fields in thedatabase. Again, typically the results of these triggers is not able tobe ascertained by examining the schema, such that in the presentexamples, the second database and associated computing modules may notbe aware of trigger results until an attempt is made to merge data fromthe second database into the first database. Thus, embodiments mayinclude functionality for surfacing errors to a user of the seconddatabase for errors caused by triggers in the first database.

Concurrency violations may also be detected in a database. Concurrencyerrors are typically raised when an attempt is made to commit data to adatabase where the data is out of date or other dependencies have notbeen met. For example some entries into some fields may only be valid solong as no changes have been made to some particular other fields.Again, these requirements can typically not be ascertained byexamination of the schema. Thus, embodiments may include functionalityfor surfacing errors to a user of the second database for violationscaused by concurrency in the first database.

However, embodiments may include adaptive features that allow a databasedeveloper of the second database to later include programmatic code toalert a user of the second database to check, trigger and concurrencyrequirements without the need to attempt to merge the data from thesecond database into the first database once such requirements are know,for example once learned by previous attempts to merge data. Forexample, the second database may be associated with a set of one or moremodules configured to store information on one or more computer readablemedia about why data from the second database cannot be merged into thefirst database so as to allow a developer to modify characteristics orconstraints of the second database.

Referring now to FIG. 3, another method 300 is illustrated. The method300 may be practiced in a computing environment and include acts forfacilitating generic database editing to allow for data to be receivedfrom a user for a first database without requiring the data to conformto a first schema for a first database. The first schema includes afirst set of constraints on data to be entered into the first database.In this example, the acts of the method 300 are performed at a seconddatabase corresponding to the first database. The second database isassociated with a second schema which has a second set of constraints.The second set of constraints is a relaxed version of the first set ofconstraints specified in the first schema. For example, as illustratedin FIG. 1, the constraints 112 may be a relaxed version of theconstraints 106. In one specific example, a constraint in the first setof constraints may limit entries into fields to integer type, while acorresponding constraint in the second set of constraints may allow forintegers, floating points, strings, and/or other data types.

The method 300 includes receiving user input for the second database,the user input comprising data complying with the second schema (act302). For example, and with reference to FIG. 1, data may be receivedthat complies with the constraints 112. The method 300 further includesstoring the user input in the second database separate from the firstdatabase (act 304). For example, parallel corresponding data for thefirst database is stored separate from the first database in the seconddatabase. In some embodiments, this allows for a parallel version ofdata that may not comply with requirements for the first database, butcan nonetheless be stored and edited and in some embodiments correctedso that it can later be merged into the first database.

In some embodiments of the method 300, the method 300 may furtherinclude importing data from the first database, storing the data fromthe first database in fields in the second database corresponding tofields in the first database, and storing the user input with the datafrom the first database in the second database. For example, if there isa need or desire to maintain a database that is fairly true to the firstdatabase, then existing data in the first database can be imported intothe second database. Data in the second database can then be added oredited in light of the existing data from the first database.Additionally, in some embodiments, this allows for known checkrequirements, triggers, and concurrency requirements from the firstdatabase to be complied with in the second database.

In an alternative embodiment, the method of claim 300 may include onlystoring data in the second database that is intended to replace data inthe first database or that is new data not yet included in the firstdatabase. For example, only data in fields in the second database thatis different in value or format from data in corresponding fields in thesecond database, or data that is entered by a user in the seconddatabase but that has not yet been merged into the first database isstored in the second database.

The method 300 may further include determining that the user inputreceived for the second database does not comply with the first set ofconstraints for the first schema for the first database, and in responseto determining that the user input for the second database does notcomply with the first set of constraints for the first schema for thefirst database, surfacing to the user that the user input for the seconddatabase does not comply with the first set of constraints for the firstschema for the first data base. For example, the second database may beaware of schema constraints for the first database, and while allowingdata to be entered into the second database that does not comply withthose constraints, the second database may nonetheless surfaceinformation indicating that data entered into the second database doesnot comply with schema constraints for the first database.

In another embodiment of the method 300, the method 300 may furtherinclude attempting to merge data from second database into the firstdatabase, receiving indication from the first database that the datafrom the second database cannot be merged into the first database, andsurfacing a message to the user that the data from the second databasecannot be merged into the first database.

As noted, the inability for data to be merged may be caused by one ormore of a number of different conditions. For example, in oneembodiment, the indication from the first database that the data fromthe second database cannot be merged into the first database may be aresult of data from the second database not complying with a checkpredicate specified by constraints in the first schema for the firstdatabase. In another embodiment, the indication from the first databasethat the data from the second database cannot be merged into the firstdatabase is a result of a trigger executing in the first database basedon data from the second database. In yet another alternative, theindication from the first database that the data from the seconddatabase cannot be merged into the first database is a result of aconcurrency violations in the first database when an attempt is made toenter data from the second database into the first database.

Embodiments of the present invention may comprise or utilize a specialpurpose or general-purpose computer including computer hardware, asdiscussed in greater detail below. Embodiments within the scope of thepresent invention also include physical and other computer-readablemedia for carrying or storing computer-executable instructions and/ordata structures. Such computer-readable media can be any available mediathat can be accessed by a general purpose or special purpose computersystem. Computer-readable media that store computer-executableinstructions are physical storage media. Computer-readable media thatcarry computer-executable instructions are transmission media. Thus, byway of example, and not limitation, embodiments of the invention cancomprise at least two distinctly different kinds of computer-readablemedia: physical storage media and transmission media.

Physical storage media includes RAM, ROM, EEPROM, CD-ROM or otheroptical disk storage, magnetic disk storage or other magnetic storagedevices, or any other medium which can be used to store desired programcode means in the form of computer-executable instructions or datastructures and which can be accessed by a general purpose or specialpurpose computer.

A “network” is defined as one or more data links that enable thetransport of electronic data between computer systems and/or modulesand/or other electronic devices. When information is transferred orprovided over a network or another communications connection (eitherhardwired, wireless, or a combination of hardwired or wireless) to acomputer, the computer properly views the connection as a transmissionmedium. Transmissions media can include a network and/or data linkswhich can be used to carry or desired program code means in the form ofcomputer-executable instructions or data structures and which can beaccessed by a general purpose or special purpose computer. Combinationsof the above should also be included within the scope ofcomputer-readable media.

Further, upon reaching various computer system components, program codemeans in the form of computer-executable instructions or data structurescan be transferred automatically from transmission media to physicalstorage media (or vice versa). For example, computer-executableinstructions or data structures received over a network or data link canbe buffered in RAM within a network interface module (e.g., a “NIC”),and then eventually transferred to computer system RAM and/or to lessvolatile physical storage media at a computer system. Thus, it should beunderstood that physical storage media can be included in computersystem components that also (or even primarily) utilize transmissionmedia.

Computer-executable instructions comprise, for example, instructions anddata which cause a general purpose computer, special purpose computer,or special purpose processing device to perform a certain function orgroup of functions. The computer executable instructions may be, forexample, binaries, intermediate format instructions such as assemblylanguage, or even source code. Although the subject matter has beendescribed in language specific to structural features and/ormethodological acts, it is to be understood that the subject matterdefined in the appended claims is not necessarily limited to thedescribed features or acts described above. Rather, the describedfeatures and acts are disclosed as example forms of implementing theclaims.

Those skilled in the art will appreciate that the invention may bepracticed in network computing environments with many types of computersystem configurations, including, personal computers, desktop computers,laptop computers, message processors, hand-held devices, multi-processorsystems, microprocessor-based or programmable consumer electronics,network PCs, minicomputers, mainframe computers, mobile telephones,PDAs, pagers, routers, switches, and the like. The invention may also bepracticed in distributed system environments where local and remotecomputer systems, which are linked (either by hardwired data links,wireless data links, or by a combination of hardwired and wireless datalinks) through a network, both perform tasks. In a distributed systemenvironment, program modules may be located in both local and remotememory storage devices.

The present invention may be embodied in other specific forms withoutdeparting from its spirit or essential characteristics. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

1. In a computing environment, a method of facilitating generic databaseediting to allow for data to be received from a user for entry into adatabase without requiring the data to conform to schema constraints forthe database, the method comprising: examining a first schema for afirst database, the first schema including a first set of constraintsspecified in the first schema on data to be entered into the firstdatabase; and constructing a second database corresponding to the firstdatabase, wherein the second database is associated with a second schemawith a second set of constraints, the second set of constraints being arelaxed version of the first set of constraints specified in the firstschema.
 2. The method of claim 1, wherein the second database further isassociated with a set of one or more modules configured to: receive datafrom a user; determine that the data received from the user complieswith the constraints in the second schema; in response to determiningthat the data received from the user complies with the second set ofconstraints in the second schema, store the data received from the userin the second database; in spite of the data received from the userbeing stored in the second database, determine that the data receivedfrom the user does not comply with the first set of constraints for thefirst schema for the first database; and in response to determining thatthe data received from the user does not comply with the first set ofconstraints for the first schema for the first database, surfacing tothe user that the data does not comply with the first set of constraintsfor the first schema for the first data base.
 3. The method of claim 1,wherein the first set of constraints includes a constraint thatrestricts field entries in a field in the first database to a limitedset of one or more types and the second set of constraints includes acorresponding constraint that allows corresponding field entries in acorresponding field in the second database to be of a type not includedin the limited set of one or more types.
 4. The method of claim 1,wherein the first set of constraints includes a constraint thatrestricts field entries in a field in the first database to be unique orprimary keys and the second set of constraints includes a correspondingconstraint that allows corresponding field entries in a correspondingfield in the second database to be entries that are not unique or validprimary keys, and wherein when data from the second database is mergedinto the first database, non conformant fields entries reportsconstraints violation and are not merged into the first database.
 5. Themethod of claim 1, wherein the first set of constraints includes aconstraint that restricts field entries in a field in the first databaseto a limited set of foreign keys and the second set of constraintsincludes a corresponding constraint that allows corresponding fieldentries in a corresponding field in the second database to not belimited to a limited set of foreign keys.
 6. The method of claim 1,wherein the second database is further associated with a set of one ormore modules configured to: attempt to merge data from the seconddatabase into the first database; receive a notification from the firstdatabase that the data from the second database cannot be merged intothe first database including information about why the data from thesecond database cannot be merged into the first database; surfaceinformation about why data from the second database cannot be mergedinto the first database; and continue to store the data in the seconddatabase in the second database to allow the user an opportunity tocorrect defects in the data in the second database that prevent the datain the second database from being merged into the first database.
 7. Themethod of claim 6, wherein data from the second database cannot bemerged into the first database for at least one of data in the seconddatabase not complying with a predicate of a check for the firstdatabase; data being rejected as a result of a trigger executing in thefirst database based on data from the second database; or data beingrejected as a result of a concurrency exception in the first databasewhen an attempt is made to enter data from the second database into thefirst database.
 8. The method of claim 6, wherein the second database isfurther associated with a set of one or more modules configured to storeinformation about why data from the second database cannot be mergedinto the first database so as to allow a user to modify characteristicsor constraints of the second database.
 9. In a computing environment, amethod of facilitating generic database editing to allow for data to bereceived from a user for a first database without requiring the data toconform to a first schema for a first database, the first schemaincluding a first set of constraints on data to be entered into thefirst database, the method comprising: at a second databasecorresponding to the first database, wherein the second database isassociated with a second schema with a second set of constraints, thesecond set of constraints being a relaxed version of the first set ofconstraints specified in the first schema: receiving user input for thesecond database, the user input comprising data complying with thesecond schema; and storing the user input in the second databaseseparate from the first database.
 10. The method of claim 9 furthercomprising: importing data from the first database; storing the datafrom the first database in fields in the second database correspondingto fields in the first database; and storing the user input with thedata from the first database in the second database.
 11. The method ofclaim 9 further comprising only storing data in the second database thatis intended to replace data in the first database or that is new datanot yet included in the first database.
 12. The method of claim 9further comprising: determining that the user input received for thesecond database does not comply with the first set of constraints forthe first schema for the first database; and in response to determiningthat the user input for the second database does not comply with thefirst set of constraints for the first schema for the first database,surfacing to the user that the user input for the second database doesnot comply with the first set of constraints for the first schema forthe first data base.
 13. The method of claim 9 further comprising:attempting to merge data from second database into the first database;receiving indication from the first database that the data from thesecond database cannot be merged into the first database; and surfacinga message to the user that the data from the second database cannot bemerged into the first database.
 14. The method of claim 13, wherein theindication from the first database that the data from the seconddatabase cannot be merged into the first database is a result of datafrom the second database not complying with a check predicate specifiedby constraints in the first schema for the first database.
 15. Themethod of claim 13, wherein the indication from the first database thatthe data from the second database cannot be merged into the firstdatabase is a result of a trigger executing in the first database basedon data from the second database.
 16. The method of claim 13, whereinthe indication from the first database that the data from the seconddatabase cannot be merged into the first database is a result of aconcurrency violations in the first database when an attempt is made toenter data from the second database into the first database.
 17. In acomputing environment, a system with functionality for facilitatinggeneric database editing to allow for data to be received from a userfor a database without requiring the data to conform to a schema for thedatabase, the schema including a set of constraints on data to beentered into the database, the system comprising: a first databaseimplemented on one or more computer readable storage media, wherein thefirst database comprises one or more database tables, columns and rows;a first schema stored on one or more computer readable storage media,the first schema defining a first set of constraints on data enteredinto the one or more tables, columns and rows in the first database,wherein at least some of the constraints are specified for a particulartable, column or row; a second database implemented in main memoryand/or on one or more computer readable storage media, wherein thesecond database comprises one or more database tables, columns and rowsincluding at least one database column, table or row corresponding toeach of one or more of the one or more database tables columns and rowsin the first database; a second schema stored in main memory and/or onone or more computer readable storage media, the second schema defininga second set of constraints on data entered into the one or more tables,columns and rows in the second database, and wherein the second set ofconstraints includes zero or more constraints on a first database tablecolumn or row in the second database that are less strict than aconstraint from the first set of constraints on a database column or rowin the first database to which the first database table column or rowcorresponds.
 18. The system of claim 17, further comprising a moduleconfigured to: import data from the first database; store the data fromthe first database in fields in the second database corresponding tofields in the first database.
 19. The system of claim 17, furthercomprising a module configured to: determine that the user inputreceived for the second database does not comply with the first set ofconstraints for the first schema for the first database; and in responseto determining that the user input for the second database does notcomply with the first set of constraints for the first schema for thefirst database, surface to the user that the user input for the seconddatabase does not comply with the first set of constraints for the firstschema for the first data base.
 20. The system of claim 17, furthercomprising a module configured to merge data from the second databaseinto the first database.